Maya 2018.6 | Vray Next 4.30.01 | PhoenixFD 4.10 Fatal error

[waaazoo]

Hi,

I have a curious problem. I installed Vray Next 4.30.01 and latest PhoenixFD 4.10 for Maya 2018 (.6 here).
When I render a scene without Phoenix stuff in Maya, it renders. When I render a Scene with Phoenix stuff it creates a fatal error // Error: V-Ray : There was a fatal error rendering the scene. //
If I render the same scene (with phoenix stuff) from the command line (mayabatch), it renders fine.
The simulation I'm trying to render was simulated with PhoenixFD 4.00. I will try to setup a quick scene from scratch with PhoenixFD 4.10.

any hints ?

[Svetlin.Nikolov]

Hey, can you tell me the exact names of the installers you used for V-Ray and Phoenix?

Sounds like a bad install for now...

[waaazoo]

I did the installation 2 times, with clean uninstall and reboot.
vray_adv_43001_maya2018_x64.exe
phoenixFD_adv_41000_maya2018_vray4_x64.exe

Meanwhile I tried a new scene from scratch, and I have the same fatal error.

I tried then to install on Maya 2019.2 (vray_adv_43001_maya2019_x64.exe and phoenixFD_adv_41000_maya2019_vray4_x64.exe) and it renders fine.

[Svetlin.Nikolov]

Trying it now, I have Maya 2018.5 here, will try it with this one and then update it if I can't reproduce it. Is there anything in the Maya log as it's loading up before you start rendering?

[Svetlin.Nikolov]

Meanwhile, can you double check if these files are there and they all have the same timestamp and size:

C:\Program Files\Autodesk\Maya2018\vray\vrayplugins:


C:\Program Files\Autodesk\Maya2018\phoenixfd\plug-ins:

[waaazoo]

file -f -new;
// Warning: file: C:/Program Files/Autodesk/Maya2018/scripts/startup/rememberViewportSettings.mel line 29: Active stereo does not work with Aero enabled. Active stereo has been disabled. //
// untitled //
commandPort -securityWarning -name commandportDefault;
// Error: line 1: Could not open command port commandportDefault because that name is in use. //
isolateSelect -state 1 modelEditor2;
isolateSelect -loadSelected modelEditor2;
onSetCurrentLayout "Maya Classic";
// Warning: V-Ray VolumeGrid: Loading shaders failed - no <*.txt> files in . //
VRayVolumeGridInit();
// Initializing V-Ray for Maya

evalDeferred "shaderBallRendererMenuUpdate";
// Warning: file: C:\Users\olivier\Documents\maya\2018\prefs\filePat hEditorRegistryPrefs.mel line 4: filePathEditor: Attribute 'aiImage.filename' is invalid or is not designated 'usedAsFilename'. //
// Warning: file: C:\Users\olivier\Documents\maya\2018\prefs\filePat hEditorRegistryPrefs.mel line 5: filePathEditor: Attribute 'aiPhotometricLight.aiFilename' is invalid or is not designated 'usedAsFilename'. //
// Warning: file: C:\Users\olivier\Documents\maya\2018\prefs\filePat hEditorRegistryPrefs.mel line 6: filePathEditor: Attribute 'aiStandIn.dso' is invalid or is not designated 'usedAsFilename'. //
// Warning: file: C:\Users\olivier\Documents\maya\2018\prefs\filePat hEditorRegistryPrefs.mel line 7: filePathEditor: Attribute 'aiVolume.filename' is invalid or is not designated 'usedAsFilename'. //
# pymel.core : Updating pymel with pre-loaded plugins: invertShape, vrayvolumegrid, vrayformaya, renderSetup, GPUBuiltInDeformer, deformerEvaluator, modelingToolkit
updateRenderOverride;
// Error: VRay: Could not load the Bifrost module! You will not be able to render Bifrost as isosurface or metaball. The error message is:[loadLib] LoadLibrary failed (126): The specified module could not be found.
//
// AbcExport v1.0 using Alembic 1.7.5 (built Feb 6 2018 18:28:0
// AbcBullet v1.0 using Alembic 1.7.5 (built Feb 6 2018 18:28:0
file -f -options "v=0;" -ignoreVersion -typ "mayaBinary" -o "W:/projets/OC_Comete/scenes/Comete_New8_8_14_18knots_200317_FD42.mb";addRecent File("W:/projets/OC_Comete/scenes/Comete_New8_8_14_18knots_200317_FD42.mb", "mayaBinary");
requires -nodeType "PhoenixFDSimulator" -nodeType "PhoenixFDLiquidSource" -nodeType "PhoenixFDOceanTexture" -nodeType "PhoenixFDPGroup" -nodeType "PhoenixFDFoam" "phoenixfd" "4.10.00";
# Phoenix Fluid Dynamics ADV for Maya 2018 / V-Ray 4.x, version 4.10.00, Build ID: 20200305

# Warning: Phoenix FD: Loading shaders failed - no <*.txt> files in . #
phxfdInit();
'C:/Program Files/Autodesk/Maya2018/phoenixfd/scripts' added to the python path.
requires -nodeType "VRaySettingsNode" -nodeType "VRaySunShape" -nodeType "VRaySunTarget" -nodeType "VRayGeoSun" -nodeType "VRayLightDomeShape" -nodeType "VRayMtl" -nodeType "VRayBlendMtl" -nodeType "VRayPlaceEnvTex" -nodeType "VRayPlane" -nodeType "VRayAerialPerspective" -nodeType "VRayRenderElement" -nodeType "VRayGeomList" -dataType "VRaySunParams" -dataType "vrayFloatVectorData" -dataType "vrayFloatVectorData" -dataType "vrayIntData" "vrayformaya" "Next";
updateRenderOverride;
// Warning: line 0: 'time1.outTime' is already connected to 'PhoenixFDOceanTexture1.currentTime'. //
# Error: You are attempting to load a file that contains legacy render layers into a scene that uses render setup. This combination is unsupported and may result in unexpected behavior. #
// Warning: line 1273: The default image may not be modified. Use the -i/image flag instead. //
import maya.app.general.mentalRayNotAvailableDialog as mrnad ; mrnad.show() ; del mrnad
// Warning: line 0: Errors have occurred while reading this scene that may result in data loss.

Please check the Script Editor for details. //
// File read in 2.2 seconds.
// File read in 2.2 seconds.
// AbcImport v1.0 using Alembic 1.7.5 (built Feb 6 2018 18:28:0
updateRendererUI;

[Svetlin.Nikolov]

Hmm, nothing fatal in the log....

[waaazoo]

Meanwhile, can you double check if these files are there and they all have the same timestamp and size:

C:\Program Files\Autodesk\Maya2018\vray\vrayplugins:


C:\Program Files\Autodesk\Maya2018\phoenixfd\plug-ins:

Yes, all files are there, same timestamp and same size as what you show

[Svetlin.Nikolov]

Roger that, so can you check C:\Users\ [your-user] \AppData\Local\Temp and see if there are any *dmp files from recent hours/minutes?

[waaazoo]

sorry, no dmp files there

[Svetlin.Nikolov]

Hmm, I'm out of ideas. Does the crash happen when you create an Ocean preset, sim 1 frame, stop the sim and render?

[waaazoo]

Hmm, I'm out of ideas. Does the crash happen when you create an Ocean preset, sim 1 frame, stop the sim and render?

Yes, I tried to sim with ocean preset based on a cube and it makes the same fatal error when you try to render. So, on your workstation with Maya 2018.5 it works well ?

But, don't worry. On my side, as it seems to work well on Maya 2019, I think I will switch to these versions for the work.

Thanks for your input.

[georgi.zhekov]

Hmm, could it be that you saved the scene after the Fatal error? What if you make a new scene - does it still show the error?

[waaazoo]

I didn't save the scene.

- scene 01 (created with Maya 2018 and previous builds from Vray Next and PhoenixFD) doesn't render on Maya 2018.6 but renders fine on Maya 2019.2
- scene 02 (created in Maya 2018 from scratch) doesn't render in Maya 2018.6
- scene 03 (no phoenixFD stuff) renders fine on Maya 2018.6

[Svetlin.Nikolov]

Very weird. Indeed I could not reproduce it with 2018.5 or 2018.6...